react-transition-group becomes regular dependency of core #1093
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes broken 1.17.0 release
@zerovox points out that changing a peer dependency like we did in #1063 is basically a breaking change as it requires action from every user.
fortunately, un-breaking the API is pretty easy: we can take
react-transition-group
on as a regular dependency, rather than a peer dependency. this is legit because it is no longer a react-addon package and does not make awkward use of theReact
global variable. it also has its own peer dependencies on react.react-transition-group
peer dependency on react is^15.0.0
so it is no longer valid to install[email protected]
alongside Blueprint (even though we technically support it). @adidahiya how acceptable is this?I also removed
r-t-g
dev dependencies from packages that don't use it (which is most of them--it's only used once inOverlay
).Reviewers should focus on
@adidahiya @cmslewis we should ship a patch release 1.17.1 after this merges to unbreak future installers. i'll be on a plane from 8:30am PST, if one of you could please handle that?